If you deploy the topic as a clustered topic, you don't need to worry about the connection to a specific node in the cluster.
In a clustered environment, the subscriptions are also split into sub-subscriptions at each cluster. If we wish to implement the nightly cron to clear the expired messages (using CLIENT_ACKNOWLEDGE and rollback), we must be able to obtain the connection manager for each cluster to clear it's local expired messages. The inability to connect to a specific cluster means this cannot be a viable solution.
It should not be necessary for a subscriber to connect to each node in order to receive all of its messages. In JBM if message sucker is configured, you can receive messages from any node in the cluster. The user guide provides detailed info about it.