title: Is there a memory leak in Castle Windsor component activator?
body: <p>I'm using Castle Windsor and DynamicProxy to implement persistence Lazy Loading from scratch (I know NHibernate could be an option etc.) I have implemented a custom component activator to always instantiate my business classes as proxies.</p>
  
  <p>I had my doubts concerning the component activator lifestyle (<a href="https://stackoverflow.com/questions/15006128/what-is-the-expected-lifestyle-of-a-castle-windsor-component-activator?rq=1">What is the expected LifeStyle of a Castle Windsor component activator?</a>). Krzysztof Kozmic kindly answered that "Every component in Windsor will get its own activator instance".</p>
  
  <p>Faced with a big memory leak in my application I have come to find that an explicit destructor in this class is never called (in my case at least). Is Castle freeing the activators appropriately, namely, when the typed factory is disposed?</p>
  
  <pre><code>Classes
      .FromAssemblyContaining(typeof(QuantityType))
      .InNamespace(typeof(QuantityType).Namespace)
      .WithService.DefaultInterfaces()
      .Configure(reg =&gt; { reg.Activator&lt;ColMsProxyComponentActivator&gt;(); })
      .LifestyleTransient() // We really want new entities every time a new one is requested
  </code></pre>
  
  <p>As a side note, would it not be useful to have the ability to explicitly declare the component activator lifestyle? In my case, there's no reason why it can't be a Singleton, and that would save some memory and processing.</p>