That is totally wrong -- Commit charge peak going above physical RAM -- does not mean that there is a memory leak.
The total commit limit of a system is the RAM + the page file
Commit charge is the current amount of memory used by all processes that resides both in the RAM and the page file
Peak commit charge is the maximum amount of committed bytes (ram + the page file usage) being used by all the processes since the last reboot
Paging is a normal activity in windows and you will do see some amount of paging no matter how much RAM you have in the box
As long as most of them are soft faults, you need not worry.
The server looks perfectly fine from the above screen shot.
Also, note that Exchange reserves memory by design and this does not mean a memory leak, Store.exe will give it back if any processes require it or if there is a memory starvation in the box.
