As the other comments have said, this is caused by issuing a composite statement to JDBC. You have a couple options.
You could do a JDBC batch. As Craig notes above this just sends each query separately in a batch.
You could write a user defined function/stored procedure with this logic and call in a single query. This has the advantage of encapsulating your db logic behind an API. The disadvantage is that without a lot of attention it becomes hard to maintain contracts between stored procedures and the application. This is an area I am doing some work on in Perl, but not yet getting there in Java.
You could collapse the query into two (your code shows three). The simple solution is:
val query1 = """ insert into gameconstants ... values ...;""" val query2 = """ insert into gamevariables ... values ... RETURNING * """
This would reduce your round trips to some extent.