We had a reflection issue with WL10's EJB3 container when I tried a couple of months ago. The Seam POJO approach (i.e., without EJB3 components) seemed to work okay on WL10.
Can you post the error messages you are getting? Maybe a good starting point is to try to get one of Seam sample apps running on WL10 first ...
There is definitely an issue with EJB vararg methods in Weblogic 10 (see stack trace below). Since Seam has quite a few vararg methods then it means that you can't deploy a full JSF->Seam->EJB3.0 application on Weblogic 10 yet.
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(jboss-seam.jar) Unable to deploy EJB: jboss-seam.jar from jboss-seam.jar: There are 1 nested errors: java.io.IOException: Compiler failed executable.exec: /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/Dispatcher_u7njda_Intf.java:20: modifier transient not allowed here public transient javax.ejb.Timer scheduleEvent(java.lang.String arg0, java.lang.Long arg1, java.util.Date arg2, java.lang.Long arg3, java.lang.Object arg4); ^ /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/TransactionListener_r4jqkg_LocalTransactionListenerImpl.java:109: modifier transient not allowed here public transient void scheduleEvent(java.lang.String arg0, java.lang.Object arg1) ^ /checkpoint/weblogic10/wlserver_10.0/samples/domains/wl_server/servers/examplesServer/cache/EJBCompilerCache/-1fp2y4mbf7ax/org/jboss/seam/core/TransactionListener_r4jqkg_Intf.java:23: modifier transient not allowed here public transient void scheduleEvent(java.lang.String arg0, java.lang.Object arg1);
Actually this problem is not just confined to Seam version 2 Beta the Weblogic bug also effects Seam 1.2 (just tried it).
Just to finish this topic off. The issue in Weblogic 10 with vararg methods has been fixed by BEA. I don't know when the fix will be available though in a production version of Weblogic 10.
This gets me a lot closer to deploying an ejb3 application.
Just an update to this issue.
The weblogic 10.3.TP tech preview does not have this fixed. I am curious though where you heard that this issue was fixed - could you let me know?
Of coarse to find that out you first have to get past the fact that the tech preview version does not work with any JPA provider for EJBs (i.e. hibernate) except for its default kodo, or openJPA.