Im gonna go ahead and reply to this myself,
The main idea here is that high coupling between any two systems is not good and is better avoided , so since exposing the queues directly increases the dependency between the two systems, this is not a good design solution.
The interface contract should never change so this should be agreed upon well in advance, so exchanging an ejb jar should be a good solution provided the interface exposed is not bound to change.
The beset approach to this is via a http call wherein a servlet
is exposed and since http communication is stateless and there is minimum dependency between the interfacing systems this is an optimal solution in general if viable.