The customer observed that removing content using REST API which was sent to trash using AdminUI beforehand leads to database and AdminUI inconsistencies.

 Steps to reproduce:
1. Create a new article "test" and note its id.
2. Send "test" to trash.
3. Delete "test" via REST API, follow API Reference.
4. Enter the trash.

Result:
You will be presented with the following error (see stacktrace.png for further details):

Could not find 'Content' with identifier 'array (
'id' => 153,
'languages' => NULL,
'versionNo' => NULL,
)'

Note:
The entry from the ezcontentobject_trash isn't removed at all. Deleting it makes trash accessible again. Besides, using Delete TrashItem method works as expected.