Adding client side call to view.remove() to fix memory leak

Not calling view.remove caused memory leaks in case of, for example, subscribing to any events in a view. This resulted in a big memory leaks, as parent views were also leaking because of parentView reference.