The legacy EJB client explicitly disabled quiet local authentication if the user hadn't already set the local authentication property and a callback handler or username was specified in the legacy properties. Since legacy EJB properties can be specified in the InitialContext environment, wildfly-naming-client needs to do this as well to make sure the specified callback handler or username will actually get used (otherwise, quiet local authentication will be enabled by default due to the changes for ELY-1158).