title: Is unhooking event handlers needed in ASP.NET to prevent memory leaks?
body: <p>Coming from WinForms/WPF I've learned the hard way that not remembering to unhook event handlers can lead to memory leaks.</p>
  
  <p>Does this apply to Webapps too?  It seems like when the request ends, everything (non-static) should be eligible for garbage collection.  Is that true?</p>
  
  <p>I remember jumping through all sorts of hoops to ensure that events got unhooked when an object goes out of scope, especially with multi-threading going on to ensure a responsive UI.  Is all of that still necessarily in a webapp or is that one of the luxuries of working with a (mostly) RESTful model?</p>