We have a enterprise archive deployment that uses slf4j + logback for logging framework. We also use managed executor service in our code. We moved to using the managed executor service so that we could get the context dependency injection that is provided by it. One of the critical things this context dependency allows us to do is leverage the cache connection manager (ccm) setup to close connections accidentally left open. 

We upgraded from WildFly 33 to 36. In WildFly 36, we find that the log statements executed in our application code as part of the managed executor service flow cannot be controlled using our slf4j + logback framework that we have built. We need to modify the standalone xml to control it. Is this behavior by design or is this a bug?