Search for my posts on this forum, I've explained the differences at least once at length.
Sorry, my question was a bit vague and misleading.
What I really wanted to confirm is that if I use @PersistentContext then Seam will not intercept this and return a Seam managed persistent context (SMPC).
I was led to think that way because I saw a seam interceptor (org.jboss.seam.ejb.SeamInterceptor) being added as an EJB3 interceptor.
But, now that I have looked at the code for SessionBeanInterceptor, the purpose of this interceptor is to detect the creation of the session bean and treat it as a seam component if the session bean has the @name annotation.
The booking example RegisterAction is using EJB3 managed PC instead of Seam managed PC.
Is this intentional? Or is it because in this specific scenario, it does not matter which one you use?
It doesnt matter in the booking demo, because there is just one component involved in the conversation. If there were lots of components collaborating, you would probably be better of with a Seam-managed PC.