More and more parts of the windows eco-system is now generated by AI and reviewed by AI, humans are only involved in testing (source is a familly member who works for microsoft). Not sure if it's the case for this app, but there might be no dev to blame here.

Just the absolute laziest implementation

There's a bunch of other requirements you need to meet and no one cares about RAM consumption. So you do it the most time efficient way, not the most memory efficient.

Before you scorn, doing it the opposite way, taking more to use less memory, makes you less promotable, not more.