The wallet keeps the secret nonce of every unfinished MuSig2 session in locked memory for as long as the wallet is loaded. A nonce is removed only when its session makes a partial signature, so each session that stops before that leaves 144 bytes of locked memory behind, with no bound on how many.
I keep at most 32768 sessions per wallet and drop the oldest first. The nonces move from each descriptor to the wallet, because every descriptor that can sign for our key in a musig() starts sessions, and each one kept its own. A dropped nonce is never reused. If no participant has added a partial signature for that MuSig2 key yet, removing our pubnonce and running round 1 again restarts the session; otherwise all participants restart the round with new nonces. A release note says so. A standard transaction has at most 1738 signed Taproot inputs, so the limit allows 18 sessions per input, enough for any tree of up to 6 signers with a MuSig2 key path and one MuSig2 leaf per k-of-n subset. At the limit a wallet's nonces use 4.5 MiB of locked memory. Unit tests fill the limit and start one more session through the same descriptor and through another one of the same wallet; they fail without the change.
This is one of several PRs from a large audit of Bitcoin Core that I did with the help of LLM tools. The audit produced its evidence all at once, which is why the PRs arrive together. I understand each change fully and will answer review questions myself.