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

@ApplicationScoped
@Traced
public class HelloWorldService {

    public String sayHello() {
        return "Hello World!";
    }
} 

leave an instance of class org.jboss.weld.contexts.CreationalContextImpl back on the heap.

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.