Error messages prefixed with "JBREM" come from JBoss Remoting. HornetQ itself doesn't use JBoss Remoting for anything. However, clients that do remote JNDI lookups (including messaging clients) do use JBoss Remoting for the JNDI lookup functionality. I'd start there with your investigation.
Be sure to treat your JNDI contexts properly (i.e. be sure to close them as soon as you are done with them).
Thanks for your findings, but in our MDB application we are not explicitly handling any JNDI connections it is configured in Spring artifact with JNDIObjectFactoryBean and messages are consumed by implementing onMessage() method of 'SessionAwareMessageListener'.
Will this depend on how other clients are calling HorentQ to push or to consume messages via JNDI look up?
I'm a bit confused about your use-case. You say you have an MDB but then you say you're using Spring and implementing onMessage() from SessionAwareMessageListener. An MDB is a Java EE technology. To my knowledge, it isn't used with Spring. Just because you have an onMessage() implementation doesn't mean you have an MDB, it simply means you have some kind of message listener.
The consuming application may not be receiving any messages because there are no messages to receive, so yes it's possible that the clients sending the messages are part of this problem. At this point I don't have enough information to say any more.