The jboss-ejb-client.xml is looked for in WEB-INF/ folder of a .war. As far as I see in the code, nothing has changed on that front. So it should still be picked up. Enable DEBUG level logging of the org.jboss.as.ee category in the logging subsystem - that should tell whether or not the file is being picked up or not.
I enabled DEBUG level logging of the org.jboss.as.ee category, and don't see any mentions aboult jboss-ejb-client.xml. Which printing rows exactly should I see ?
It worked for me after I put jboss-ejb-client.xml into "resources" folder of war. Now I see:
2018-02-15 11:08:29,677 DEBUG [org.jboss.as.ee] Successfully parsed jboss-ejb-client.xml for deployment unit deployment "npp.war".
Please fix when jboss-ejb-client.xml in WEB-INF folder. I think there is a small bug in code of Wildfly 11.
Can you paste the output of the following command, both when the file is parsed and when it isn't:
jar -tf yourwarname.war
Run it against the file which actually gets deployed.
I checked the issue more deeply, and put attention jboss-ejb-client.xml sometimes parsed from WEB-INF, and sometimes - not, during starting the application. In most of cases it is parsed, so let's assume it is OK.
In any case, it doesn't override jndi.properties, and InitialContext works according to jndi.properties.