bean-validation quickstart fails to start managed container

The Arquillian tests fail on the bean-validation quickstart when run against a managed JBoss server as in the following output.

Updating to use the jboss-javaee-6.0-with-tools version 1.0.0.M4 in pom.xml seems to fix the issue.

$ export JBOSS_HOME=/home/david/Apps/jboss-as-7.1.1.Final/
$ mvn clean test -Parq-jbossas-managed
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building JBoss AS Quickstarts: Bean Validation 7.1.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] — maven-clean-plugin:2.4.1:clean (default-clean) @ bean-validation —
[INFO] Deleting /home/david/Development/Java/quickstart/quickstart/bean-validation/target
[INFO]
[INFO] — maven-resources-plugin:2.5:resources (default-resources) @ bean-validation —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] — maven-compiler-plugin:2.3.1:compile (default-compile) @ bean-validation —
[INFO] Compiling 1 source file to /home/david/Development/Java/quickstart/quickstart/bean-validation/target/classes
[INFO]
[INFO] — maven-resources-plugin:2.5:testResources (default-testResources) @ bean-validation —
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO]
[INFO] — maven-compiler-plugin:2.3.1:testCompile (default-testCompile) @ bean-validation —
[INFO] Compiling 1 source file to /home/david/Development/Java/quickstart/quickstart/bean-validation/target/test-classes
[INFO]
[INFO] — maven-surefire-plugin:2.10:test (default-test) @ bean-validation —
[INFO] Surefire report directory: /home/david/Development/Java/quickstart/quickstart/bean-validation/target/surefire-reports

-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.jboss.as.quickstarts.kitchensink.test.MemberValidationTest
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
Mar 15, 2012 19:43:25 AM org.jboss.as.arquillian.container.managed.ManagedDeployableContainer startInternal
INFO: Starting container with: [/usr/local/java/jdk1.7.0_03/bin/java, -Xmx512m, -XX:MaxPermSize=128m, -Djboss.home.dir=/home/david/Apps/jboss-as-7.1.1.Final/, -Dorg.jboss.boot.log.file=/home/david/Apps/jboss-as-7.1.1.Final//standalone/log/boot.log, -Dlogging.configuration=file:/home/david/Apps/jboss-as-7.1.1.Final//standalone/configuration/logging.properties, -Djboss.modules.dir=/home/david/Apps/jboss-as-7.1.1.Final//modules, -jar, /home/david/Apps/jboss-as-7.1.1.Final/jboss-modules.jar, -mp, /home/david/Apps/jboss-as-7.1.1.Final//modules, -logmodule, org.jboss.logmanager, -jaxpmodule, javax.xml.jaxp-provider, -mbeanserverbuildermodule, org.jboss.as.jmx, org.jboss.as.standalone, -server-config, standalone.xml]
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
Invalid option '-mbeanserverbuildermodule'
Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]
java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]
java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]
java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]
where <module-spec> is a valid module specification string
and options include:
-help Display this message
-modulepath <search path of directories>
-mp <search path of directories>
A list of directories, separated by ':', where modules may be located
If not specified, the value of the "module.path" system property is used
-class Specify that the final argument is a
class to load from the class path; not compatible with -jar
-cp,-classpath <search path of archives or directories>
A search path for class files; implies -class
-dep,-dependencies <module-spec>[,<module-spec>,...]
A list of module dependencies to add to the class path;
requires -class or -cp
-jar Specify that the final argument is the name of a
JAR file to run as a module; not compatible with -class
-config <config-location>
The location of the module configuration. Either -mp or -config
may be specified, but not both
-jaxpmodule <module-name>
The default JAXP implementation to use of the JDK
-version Print version and exit

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.13 sec <<< FAILURE!

Results :

Tests in error:
org.jboss.as.quickstarts.kitchensink.test.MemberValidationTest: Could not start container

Tests run: 1, Failures: 0, Errors: 1, Skipped: 0