It's not a bug. SSMS is a 32-bit application and as such can use no more than 2GB of memory, no matter what is available. Profiler does not display all the execution plans as SSMS does, hence it uses less memory at any point.

As an aside, you should not be running SSMS on the server as it will be taking memory and resources away from SQL Server. Run SSMS on a remote workstation and connect to the server.