title: The best way to undelegate events once a view is no longer needed
body: <p>Is it a bad practice to call <code>undelegateEvents()</code> in the view <code>remove()</code> method? Why wasn't it included by default by the backbone guys?</p>
  
  <p>I realized I am falling into so many binding issues, when simply reinitializing a view variable. Although <code>undelegateEvents()</code> is being called automatically when a new view is created, it is trying to undelegate events for the newly instantiated view, not the previous one. Therefore, unless manually calling it every time, ghost event callbacks remain alive and screw up my apps.</p>
  
  <p>What's the best way to handle this? </p>