Remove JNDI port from standalone.xml/domain.xml

JNDI port was erroneously included in configuration files. It is not used and must be removed (leads to confusion).

Original Description:

"Many many customers use client lookups of JNDI contexts to get at what used to be called remote interfaces to invoke EJBs on a JBoss instance. Where and how does this work? Is this be design? If so, this is going to be a problem for many current customers, as they do this today."