Here is how I ended up getting it to work. Though not tested yet. But deployed.
First, I removed the second project out of my Workspace so that the ranch EJB, Client, and EAR is all thats there.
Then, I created packages for the eao and the entities for the accounts classes I needed.
I then right clicked the package and selected New then other then in general I selected File.
Then clicked advanced and selected Link to file in the file system.
Then browsed to the files I needed in this project
Then clicked Finish.
I repeated this for my eao classes and my entities needed.
Once I had everything added to my project, it compiled. Do note that I had already referenced the persistent
unit in the eao and I already had the second persistent unit in the persistent.xml file.
Now that it compiled, I deployed. And it deployed. But it only deployed what I needed rather than the entire accounts projects Jar file.
The one benefit to this is that the files I added are linked and so any changes I make to accounts is reflected in ranch and visa versa. I just have to make sure I deploy both if I make a change.
Now, with this said. Is there any issues with doing it this way? Again, I have not yet tested it .