Strange that support RMA-ed the APs for an out-of-memory problem, as the replacement AP is supposed to have the exact same amount of memory. What is more likely is that you have a specific feature turned on that introduces a memory leak in one of the processes running on the AP. And TAC should be able to see where memory is going and what is taking up the memory. You could even do that yourself with the 'show cpu details' and 'show process' commands, and compare that over time. Another thing would be to disable any feature (not used) except that basics and when the memory leak is gone start turning on again.
Please work with your local Aruba SE to get assistance with your TAC cases, without knowing the further context, the approach chosen doesn't sound right. Asking TAC for escalation in your case may help as well.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------