Some JSON requests are modified by Hash::MultiValue

I noticed that for some JSON body parameter schemas, arrays are sometimes simply removed when deserialized and stored in request->body_request()
For example, this JSON body parameter:

{
  "foo": [ { "bar": 1 } ],
  "baz": { "foobar": [ { "blah": 2 } ] }
}

will be parsed into this in a route:

$VAR1 = {
          'foo' => {
                     'bar' => 1
                   }
          'baz' => {
                     'foobar' => [
                                   {
                                     'blah' => 2
                                   }
                                 ]
                   },
        };

Notice that the "foo" field is no longer an array after the deserialization, but the "foobar" field is as expected. I can reproduce this in both 0.202000 and 0.203000.

I tracked it down to the use of Hash::MultiValue->from_mixed(), and with this naive patch it works as expected for me:

--- Dancer2/Core/Request.pm.orig    2016-09-02 11:05:27.042773871 +0200
+++ Dancer2/Core/Request.pm 2016-09-02 11:05:35.714634529 +0200
@@ -213,8 +213,8 @@

     # Set body parameters (HMV)
     # Not happy with fiddling with Plack::Request internals -- veryrusty Aug 2016.
     $self->env->{'plack.request.body'} =
-        Hash::MultiValue->from_mixed( ref $data eq 'HASH' ? %$data : () );
+        Hash::MultiValue->new( ref $data eq 'HASH' ? %$data : () );

     return $data;
 }

I expect my "solution" to break more than it fixes, but I hope that you experts can come up with a better solution.