 to the LogFactory1 instance (as normal) and a strong reference from
 the LogFactory1 instance to the component classloader via
 <code>getClass().getClassLoader()</code>. This chain of references will prevent
 collection of the child classloader.
 <p>
 Such a situation occurs when the commons-logging.jar is
 loaded by a parent classloader (e.g. a server level classloader in a
 servlet container) and a custom <code>LogFactory</code> implementation is
 loaded by a child classloader (e.g. a web app classloader