I exactly added the class you mentioned from Seam 2.3 to Seam 2.2 and yes I'm using Maven.

unlike the sample you pointed I'm trying to deploy an EAR file as following in Arquillian

@Deployment(testable = false) 
    public static Archive<?> createDeployment() 
    { 
        //TODO : get from System.getProperties(testDeployment) 
        String testDeployment = "/home/omidbiz/blog-ear/target/blog.ear";//can not deploy exploded archive 
        String deploymentName = testDeployment.substring(testDeployment.lastIndexOf("/") + 1); 


        Class<? extends Archive<?>> deploymentClass = EnterpriseArchive.class; 


        return ShrinkWrap.create(ZipImporter.class, deploymentName).importFrom(new File(testDeployment)).as(deploymentClass); //there is no addAsWebInfResource for EnterpriseArchive
    } 

which I took from https://github.com/seam2/jboss-seam/blob/Seam_2_3/functional-tests/src/main/java/org/jboss/seam/example/common/test/DeploymentResolver.java

can I deploy a Seam EAR file into Arquillian ? (the EAR file successfully runs in JBoss AS 7)

I managed to solve the previous error now I get the following exception

java.lang.IllegalArgumentException: EntityManagerFactory not found in JNDI : java:/myseamEntityManagerFactory
  at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:261)

Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
  at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
  at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
  at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344)
  at javax.naming.InitialContext.lookup(InitialContext.java:411)
  at org.jboss.seam.persistence.ManagedPersistenceContext.getEntityManagerFactoryFromJndiOrValueBinding(ManagedPersistenceContext.java:257)
  ... 103 more

I don't understand the Arquillian if it's using the jboss that I define in arquillian.xml then everything should be ok

arquillian.xml

<arquillian xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://jboss.org/schema/arquillian"
    xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd">


    <defaultProtocol type="Servlet 3.0" />


    <engine>
        <property name="deploymentExportPath">target</property>
    </engine>
  
    <container qualifier="jboss7" default="true">
        <configuration>
            <property name="jbossHome">/home/omidbiz/jboss-eap-6.2/</property>
            <property name="javaVmArguments">-Xms512m -Xmx512m -XX:MaxPermSize=512m -Djava.net.preferIPv4Stack=true -XX:-UseSplitVerifier</property>          
        </configuration>
    </container>


</arquillian>

TestCase.java

@Test
    public void simpleEntryTest() throws Exception
    {


        String id = "simpleBlogEntry";
        String title = "Simple blog entry";
        String excerpt = "This is an excerpt";
        String body = "This is a simple blog entry posted for testing purposes.";


        System.out.println(id);
        new ComponentTest()
        {


            @Override
            protected void testComponents() throws Exception
            {
                DBUtil du =  (DBUtil) getValue("#{dbUtil}");
                System.out.println(du.getEntityManager()); // this line throw the exception
            }
          
        }.run();
    }

I also realize that seam-integration-tests module is using Arquillian differently with packaging a war file after I changed my test module I get this exception

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS014395: Could not load component class org.jboss.seam.mock.MockSeamListener"}}