The ability to support an arbitrary number views on to the same model might be considered as the defining characteristic of MVC. With that in mind, for a MVC app to support a new view being created, being used for a bit, then going away is just "business as usual". I'm guessing that's why Ilja is asking for clarification on what problems you are having.
As a small example, the MVC command-line caclulator from
this old thread allows users to create/destroy new views "on the fly".