Most of the WildFly code uses message format patterns for debug logging in order to avoid unnecessary allocations in normal operation. The EJB3 subsystem client seems to be one of the few places where this is not yet the case and debug messages are always created even if the debug logging is disabled.