for the very simple cases the recommended solution would be to rely on the jpa providers built in 'import sql' features.
e.g. with Hibernate add a file named import.sql to the classpath of your deployment. Hibernate will then pick up the file and execute the sql statements during deploy. Not sexy like Persistence Extension, but it work..
This is something we should attempt to support via the Persistence Extension in the future, but the Persistence Extension is currently blocked by how Arquillian Core handles the execution in a @Deployment.testable=false/@RunAsClient scenario.