title: Do I need to register Ninject.OnePerRequestModule with Ninject.Web.MVC 3.0?
body: <p>I'm using Ninject for DI and the Ninject.MVC3 extension within an MVC4 app, specifically version 3.0.0.6.</p>
  
  <p>Reading the <a href="https://github.com/ninject/Ninject.Web.Common/wiki/InRequestScope" rel="nofollow noreferrer">documentation</a> on Ninject's wiki, it appears that the lifetime of objects created with <code>InRequestScope</code> are actually controlled by ASP.NET and to properly clean up one should register the <code>OnePerRequest</code> HttpModule.</p>
  
  <p>However it looks like this doco is out of date as <code>type="Ninject.OnePerRequestModule"/&gt;</code> cannot be found.</p>
  
  <p>On the other hand I read some <a href="https://stackoverflow.com/questions/5018333/ninject-and-oneperrequestmodule">bits</a> recently that seemed to suggest that <code>NinjectHttpApplication</code> already deals with <code>OnePerRequest</code>.</p>
  
  <p>My question is whether Ninject.Web.MVC 3.0 already deals with this issue or if I still have to manually add the HttpModule to my 'web.config'.</p>
  
  <p>I have added the below to my config and everything appears to be working, though I have no idea at all how to test for when objects are destroyed:</p>
  
  <pre><code>  &lt;system.web&gt;
      &lt;httpModules&gt;
        &lt;add name="OnePerRequestModule" type="Ninject.Web.Common.OnePerRequestHttpModule"/&gt;
      &lt;/httpModules&gt;
      ...
  </code></pre>
  
  <p>Do I need to manually add the <code>OnePerRequest</code> HttpModule or does Ninject.Web.MVC handle this for me?</p>