Thanks drew, that's what I thought. It's the same as MySQL.
The array is compiled of many different language files for all the modules in a CMS I'm building. Since the modules need to have access to values and "words" in any other module at any given time, I need to load all the language files and have them ready to be accessed. So this array happens to be ~75K in size with 9 modules, but I expect that to grow as I continue to develop more features. The thing that I need to keep reminding myself of is that it's a CMS, not a website. It will only be used by a client as often as a few times a day (most likely a few times a week), so it doesn't need to be extremely efficient with the resources... but I do want to try my best.
I do have my own internal timer for debugging the code. If I try to separate the language files into two types: "global" for shared language values, and "local" for language values that would be used by that module alone... then I will increase the speed of my script by 10% (a few milliseconds), but it would mean many different changes elsewhere that I am unwilling to make.