This was intentional.
The delete plugin only takes care of the very simple and straight forward delete cases. There may be other areas that aren't covered by the plugin. Notably with custom fields (and prefixes) we couldn't guarantee that all implementations would be identical and not doing custom things in their controller code and templates so we decided to bypass the delete plugin here.