There have been more than a couple of users who have run into problems where the auto created remoting connections from a remote EJB client, timeout after a certain amount of inactivity and subsequent invocation fails with a remoting exception before a reconnect attempt is handled by the EJB client API.

It would be better to configure the org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL (in milli seconds) to some reasonable value, by default on such connections and allow user applications to opt-out of it if necessary.

More details in the referenced forum threads.