Wrong routing of EJB calls in cluster

This issue is a regression, so the priority is blocker. This issue has been caused by this commit, you can check that the the reproducer passed with the previous WF revision 9c47af2ab184e23b6657de2b4be97a9dea70ac10.

Steps to reproduce

• git clone https://github.com/wildfly/ejb-client-testsuite .
• cd multinode
• mvn -f pom-wildfly-client/pom.xml clean install -Dprepare -Dserver.zip.url=file:///path/to/server.zip
• mvn -f pom-wildfly-client/pom.xml -Dmaven.test.failure.ignore=true -Ptestrun test -Dmaven.test.redirectTestOutputToFile=true -Dtest=ClientInvokingTwoClustersStatelessBeanTestCase#testInvokingTwoClustersAlternately

Full list of affected tests

• ClientInvokingTwoClustersStatefulBeanTestCase.testInvokingTwoClustersOneAfterAnother
• ClientInvokingTwoClustersStatefulBeanTestCase.testInvokingTwoClustersAlternately
• ClientInvokingTwoClustersStatelessBeanTestCase.testInvokingTwoClustersOneAfterAnother
• ClientInvokingTwoClustersStatelessBeanTestCase.testInvokingTwoClustersAlternately