On EJB3 again

So, recently I have posted the whole test project on my website. It is now available through this link so you can grab it if you want. This piece of code is designed to run on GlassFish build 34 and as a backend database it uses Oracle XE with HR scheme enabled.
Yesterday evening I successfuly overode annotations by xml descriptors so now I know how to do it. This is not a magic - just use your EJB 2.1 style descriptors and everything will be just fine. For more see example of EJB3Servlet - there is a call to fooQeueue that is actuelly mapped to testQueue.
What is now bear in my mind is perfomance of entity beans - it's back to the root problem because I didn't solve it yet and this problem occured in the begging of my work. I hope the persitence layer is somehow "confused" by so many circular mappings. I'll try to eliminate some of them (for example mappimg emloyee-manager department-manager and so on) and hope it helps.
Last week I found a great community of same thinking people around EJB3 at glassfish forum. They helped me to solve my initial problem with message driven bean (the problem when I forgot to implement MessageListener interface). Yesterday I posted there another problem and hopfuly they'll help to find some solution. It's about NativeNamedQuery but you better see for yourself here.
I don't know exactly what I'm goind to do next but I'll choose from these:

As part my certification preparation, improve example application by adding more features of Java 5.

Add Wicket support (even without any Java 5 or EJB3 feature) just to get familiar with this powerful framework

Try out Caché database. This "post relational" database has many uniques - it doesn't require object-relational mapping as data are stored as objects ! It would be fun :-)
As you can see, I have a lot of challenges ahead ... And no time to waste :-)