MDR AnnotationCreator/AnnotationProxy leads to proxy leakage

[jason.greene]

The current code in AnnotationCreator and AnnotationProxy reuse the classloader that defines an annotation to create the new proxy in. This is bad when the annotation exists in a classloader that stays around for a long time, like say one that would hold jboss annotation classes :)

Instead we should be passing these routines a short-lived loader to define the proxies in.

[alesj]

Instead we should be passing these routines a short-lived loader to define the proxies in.

The AnnotationCreator takes a ctor which has cl as param,
we should make sure this gets used.
And then the AnnotationProxy should use that one instead of annotation's.

I just doubt we always have the right cl present that we could push into AC.