Dealing with Memory Pressure problems in MOSS/WSS

Here's a great link about memory pressure problems in MOSS/WSS. It ends concluding:

In ASP.NET there are more or less 3 approaches for this:

1) Follow all the steps outlined above to ensure that your application only allocates the memory it really requires (this is the approach you always should follow first!)

2) Using the /3GB switch? - sorry this cannot be used with SharePoint!
Although this solution would allow ASP.NET to use around 1.8 GB of memory before running into memory pressure situation it cannot be used with SharePoint.
The following article explains why using the /3GB switch in SharePoint is not an option:
http://support.microsoft.com/default.aspx/kb/933560

3) Switching to 64-bit architecture
In 64-bit architecture the virtual address space is no longer limited to 2 GB. This also means that memory fragmentation as discussed in the beginning of this article will not have the negative effects as in 32-bit architecture and the 800 MB limitation for ASP.NET does no longer exist.