You can capture a memory dump of the offending process on the remote machine and then analyse the dump using WinDbg / sos.dll (http://msdn.microsoft.com/en-us/library/bb190764.aspx) on your local machine.
The SOS debugging extension will (among other functionality):
- Give you statistics on the managed heap such as generation sizes, type names / allocation size, etc.
- Allow you to trace the roots to objects on the managed heap which may give you clues as to which parts of your app are responsible for excessive memory allocation.