I've not explored every program domain, but in general I see two kinds of program memory access patterns.

The first is a fairly generic input -> transform -> output. This is your generic request handler for instance. You receive a payload, run some transform on that (and maybe a DB request) and then produce a response.

In this model, Arc is very fitting for some shared (im)mutable state. Like DB connections, configuration and so on.

The second pattern is something like: state + input -> transform -> new state. Eg. you're mutating your app state based on some input. This fits stuff like games, but also retained UIs, programming language interpreters and so on on.

Using ARCs here muddles the ownership. The gamedev ecosystem has found a way to manage this by employing ECS, and while it can be overkill, the base DOD principles can still be very helpful.

Treat your data as what it is; data. Use indices/keys instead of pointers to represent relations. Keep it simple.

Arenas can definitely be a part of that solution.