Yep, looks like this issue was fixed with yesterday's macOS 12.3.1 (21E258) release.