Just take a look at my reply again, you will find "stand-alone client application" phrase, I think even a beginner to EJB3 knows that you can have a reference of a local EJB in another local module using annotations;)
Noticing the exception  you've written, I imagined by myself you were going to call a Session Bean from a stand-alone client application. Not to mention anything about application-client.xml, and not to set any JNDI properties made me predict you were waiting for a miracle, ;) and I thought you were just trying to connecting to an SB in a bloody and disaster approach, that's why I suggested you the simplest and fastest way. however I'm not sure looking up an enterprise resource is a disaster but the best way for a simple stand-alone client. ;)
But to develop a Java EE Application Client, (the way you are looking for) I've found Sun Java EE Tutorial damn great, refer to CREATING THE APPLICATION CLIENT. if you are going to handle it. you must run your client with a batch file called appclient.bat (.sh) in glassfish. To know how to make your client free of app server, analyze appclient.bat.

I myself prefer to have a JAXWS webservice tier between, that makes everything simple, I guess it's better to let Java EE app servers talk to each other directly not a client to a server.