Bug: When deleting Canvas containing non-existing views, it leaves stranded nodes

I have Canvas’ with View revisions that has been deleted. If I delete the “object” directly in the Canvas, it works well. However, if I delete the Canvas directly without first deleting the objects, I get stranded nodes (FdmInstanceContainerReference nodes). 
If I delete a Canvas with object linking to existing View revisions, it works well.

Would be nice if this was fixed since getting Canvas’ with outdated revisions is relatively common in a period with heavy data model development (revisions are constantly bumping, and we need to clean old revisions to stay below the view/revision limit). Now we are forces to run cleanup scripts on stranded canvas nodes on a regular basis