Potential memory leak when using opentracing -------------------------------------------- Key: WFLY-14094 URL: https://issues.redhat.com/browse/WFLY-14094 Project: WildFly Issue Type: Bug Components: CDI / Weld, MP OpenTracing Affects Versions: 19.0.0.Final, 19.1.0.Final, 20.0.0.Final, 20.0.1.Final, 21.0.0.Final Reporter: Michel Erard Assignee: Matěj Novotný Priority: Major Labels: downstream_dependency Fix For: 22.0.0.Beta1 Attachments: bad_heapdump.png, good_heapdump.png, image-2020-11-23-11-59-50-907.png Depending on the CDI/EJB scope the usage together with opentracing can end up in a memory leak. Here I did a little sample project to simulate the issue:  [https://github.com/erard22/wildfly-memory-leak] Requests handeled by this class {code:java} @ApplicationScoped @Traced public class HelloWorldService { public String sayHello() { return "Hello World!"; } } {code} leave an instance of class {{org.jboss.weld.contexts.CreationalContextImpl}} back on the heap. !bad_heapdump.png! Also when using {{@Stateless}}. It disapears when you change to {{@Dependent}}. I did some tests with different versions. It seems the issue was introduced with wildfly-19. Before it worked. I also did it with EAP. There it was fine with 7.3.0 but is now present in 7.3.3.