Hi David,
The workflow for users who require the ability to work with views, is to access the view as a query layer or simply drag/drop the view (assuming it has a spatial attribute) into the map and define the required properties when necessary.
The workflow you have described can lead to unknown behaviors and errors in the application (ArcObjects) when working with this object. The reason is because, the object they are deleting is a geodatabase table and we support additional capabilities on tables that we cannot support on views.
With that said i would be interested in hearing more about situations where a view needs to be registered with the geodatabase. Could you describe workflows where you have required this capability?