AA 3.0: Freeing Memory?

I've noticed that after running multiple processes in AA 3 (Edit View) my memory consumption jumps considerably and it appears to be cumulative with each successive process that's run.  And, after those processes are completed, AA doesn't seem to release it (RAM).  I guess it's not a huge problem because I have a fair amount of memory, but is there any way of getting AA to release memory periodically -- or to manually release it?  Obviously, closing the program frees it up again, but that seems like about the only time it happens.

What sort of processes?

Maybe you could explore doing the same in multiview and the use of busses to conserve ram & cpu?

Edit View can work with many levels of Undo, and in order to do this it has to use Temp files.  If you put a file into Edit View, then process it, the original file still stays in memory and the processed file stays in Virtual Memory until you either save it as another file or overwrite the original file.  The more process steps you do without saving, the more Virtual Memory is used to store each process step. 
That's why, when you finally save a file in Edit View after editing and/or processing it, you see the dialogue box "Flushing Virtual Memory" come up before it saves the file. 
Runaway has good advice.  Multitrack view is non-destructive to the original wave and you can pile on as many processes as your computer system will allow. 

If you get too worried you can manually flush the Virtual Memory from the File menu. Also there is the option to manage Temporary Folder Reserve Space which allows you to selectively close files or clear some of your Undo History.

if you are one of the people using Vista, this is a known issue with Vista . . . currently only think I know that recovers all memory is a system reboot

(admittedly this is an issue with all MS OS ... . it's just that issue on networked multicore systems the issue seems worse to the point of being crippling with Vista

There is a lot of good advice here and if heeded will certainly (within reason) maximise available ram.  But as you say you have plenty and I guess this more an enquiry than a problem.

As indicated I do most of my work in MV which as Eric points out is non destructive and for a heap of other reasons is ideal for me.  Even so I can sometimes (attempt to) create an undo file > than 4gb.  Being reasonably lazy (or forgetful) I never take ryclark's good advice (though I should) and clear my undo history (even though I am never going to be able to or want to undo back 4gbs!)

I only have 2gb ram and really (apart from the undo history which only rears its head at mixdown time) thats heaps so I wouldn't pay too much attention to how much ram is being used as you use AA