Bug - field definitions with same internal name cause conflict

Hi,

I'm in the process of migrating a solution from SP2010 to SP2013.

I have a feature that contains a bunch of field definitions. One of the fields is declared as follows:

<Field ID="{594BAF99-9FCA-4c4b-A744-D9F37300024A}"
         Name="Description"
         Group="MyGroup"
         Type="Note"
         DisplayName="MyDisplayName"
         SourceID="http://schemas.microsoft.com/sharepoint/v3/fields" />

When I try to activate this feature in a site collection, I get the following exception: 'A duplicate field name "Description" was found.'

Narrowing down the issue, I found out that the conflict refers to the "Description" field declared in the standard "Fields" feature (in the fieldswss3.xml file located in /15/template/features/fields folder):

<Field ID="{3f155110-a6a2-4d70-926c-94648101f0e8}"
        Name="Description"
        StaticName="Description"
        SourceID="http://schemas.microsoft.com/sharepoint/v3/fields"
        Type="Note"
        DisplayName="$Resources:core,GBW_FC_Description_Field;"
        Group="_Hidden"
        Sealed="TRUE"
        ReadOnly="TRUE">

Notice that, eventhough the internal name is the same in both fields, the "Group" is different.

This worked fine in SP2010. Is it a bug on SP2013? Can anybody tell me if there's a chance this will be fixed in a future release?