Running a simple EJB is showing what appears to be a memory leak in WeldListener.

You can see the memory leak by putting breakpoints in the following locations:
WeldListener.requestInitialized line 193
conversationContextActivator.associateConversationContext(request);

WeldListener.requestDestroyed line 152
conversationContextActivator.deactivateConversationContext(request)

If you observe the conversationContextActivator->httpConversationContext->creationalContext->dependentInstances
you will see the number of items in the dependentInstances list increase each time you execute the url (it appears to increase by 4 in this example).

The instances are actually being held by CreationalContextImpl->parentDependentInstances. I can see where they are added but I do not see an equivalent remove.

I tested the app on GlassFish and JBoss and the behavior exhibited by WeldListener is identical.