>The app works great and reliable but after the process runs between 500-900
>times (which is NOT unusual for the app) the user sees something they refer to
>as a memory leek, i.e. in their resources they see the available memory slowly
>increasing until BAMMM the sucker crashers.

A memory onion, huh? :-)

Tell them to check and make sure they're explicitly releasing variables when returning from procedures -- this has been known to help in some cases.