Difference in return results of withCriteria between Unit and Integration Tests with projections

The withCriteria method on Domain classes returns different result structures when running in Unit and Integration Tests when using projections. In Integration Tests (verified in 2.0.1 and 1.3.6), if multiple projections are stated for a withCriteria call, then the results are returned as though they are in 1 row:

Foo.withCriteria {
  projections {
    rowCount()
    sum 'amount'
}

Returns an object that looks like

[[<rowCount>, <sum>]]

However, in 2.0.1 Unit Tests, the same project is decomposed from the wrapper list and returns --> [<rowCount>, <sum>]

This makes code that uses withCriteria and projections untestable using UnitTests because the results return differently than they do in integration tests and in run-time

I've attached a test project that has the same test methods in both a unit & integration test. The Integration tests pass and the unit tests fail.

I've traced this all the way down to the difference between org.hibernate.loader.Loader.doQuery:829 and org.grails.datastore.mapping.simple.query.SimpleMapQuery (starting at line 77)
The SimpleMapQuery iterates through each projection and adds it to the result list, where as Hibernate performs the query which returns a row with all the projections and adds the row to the result list (thus the double list wrapping).

The funny thing is the the UnitTest implementation behavior matches the Grails documentation: http://grails.org/doc/latest/ref/Domain%20Classes/withCriteria.html