In our case, this was remediated in CU4 for SQL Server 2012 SP1.

An update is available for SQL Server 2012 Memory Management

http://support.microsoft.com/kb/2845380

CU4 for SQL Server 2012 SP1

http://support.microsoft.com/kb/2833645/en-us

http://www.sqlservercentral.com/Forums/Topic1415833-2799-3.aspx#bm1458905