This is due to the call to FileDAO.remove() with the file model that has been augmented with previews and sections. A call to removeById() should fix this.

This might also be related to the fact that the file still shows up in ElasticSearch. Somewhere in the code there should be a call to ElasticSearch.reindex() with the file id.