I think it’s partially a philosophic question of “what is the purpose of a bug / ticket tracker?”
Some people treat their ticket list as a historic record of defects found, whether or not they are being actively worked on or whether or not there is even a plan to fix them. To these people, the bug list is documentation of all the software’s issues.
Other people treat the bug list as their work checklist. Tickets are a working set of things we are actively working on and plan to resolve. If you don’t have a plausible plan to fix the bug, you close it as “won’t fix”.
I find camp 1 just accumulates and accumulates and the bug list becomes this long menu that you have to periodically groom and pick from. I happen to fall in camp 2 and am very aggressive about closing things that will realistically never be fixed. My bug list is what I actually have a plan to resolve.
When you get both camps in one company, it gets confusing and you end up with these “bankruptcies.”
if it is an actual issue that ought to be fixed but you don't have the resources to do it, then it could be moved to a backlog instead closing it as "won't fix". the backlog is the documentation of all the issues and it is clear that there is no plan to fix something in the backlog. that way it works for both types.