This is all correct but I'm not sure it answers the original question. Geronimo datasources/database pools are designed to only be accessed in the same VM as they are deployed in. You cannot look up a database pool deployed in geronimo from another VM no matter how you configure the remote jndi. One reason for this is that we don't have a distributed transaction manager and certainly couldn't come up with a correctly configured transaction manager in the remote vm through a jndi lookup.
If you really want a "standalone" application to be able to use a geronimo datasource consider deploying the app in the app client container and deploying the datasource there.