OK, I read that page 278, and I believe all it's saying is that ejbSelect calls
can return something besides the component interface or a collection of the component interfaces, not that it has to. An ejbSelect could also return a component interface or a collection of them, but then why not use a finder? Anyway, a home business method, in fact, could return a component interface, by calling an ejbSelect method. The bean would still be in the pool though, and in no way related to the remote interface(s) it was returning. The first time the client called a business method on that remote interface, the container would pull a bean out of the pool and call its ejbLoad method. It would be a strange coincidence if the bean instance pulled out of the pool was the same bean instance that executed the home business method.
B Satish's example is also correct. In fact, you can get the home interface from the ejbHome methods, so you could skip the JNDI lookup.
Great question, by the way. I think I've got everything straight in my mind now, but I'll be checking back to see if there are any corrections.