You can not access the DS from a remote client. It can only be accessed from within the server VM.
I am curious as to what the rationale is for making the DS not accessible from outside JBoss.
Given a use case that involves external scripts that run against the DB, without being part of the JBoss deployment, and given that these "scripts" have their own DAO and want to be connection-pool savvy, how would one go about obtaining the DataSource in question?
Write a server side component, such as SLSB or MBean that talks to the datasource, rather than requiring the scripts to connect to a remote DS directly (connecting remotely to a connection pool makes little sense).