Hearthstone (PC client) is leaking memory/resources

This bug might be on Mercenaries side only, but here’s some data to show what’s going on. Repeating bounty 1 in barrens with same team, so there shouldn’t be any new resources loaded after first round. Snapshot of data taken at the beginning of first battle of the bounty, while waiting to drag mercs onto the field, just to have identical spot where you’d expect cpu/memory consumption to remain steady (my team = diamond N’Zoth with his fancy rain graphics + Murky). It’s not a fast leak, but at least with my habit of having the game running on the background for hours, it becomes eventually very visible. Highest I’ve seen in the past was over 2600MB memory consumed, that’s what triggered me to do this test. All values grabbed from Task Manager.

Bounty 1: 6.0% CPU, 774 MB memory, 6.9% GPU
Bounty 2: 10.5% CPU, 860 MB memory, 12.8% GPU
Bounty 3: 9.9% CPU, 746 MB memory, 9.8% GPU
Bounty 4: 10.8% CPU, 774 MB memory, 9.3% GPU
Bounty 5: 12.5% CPU, 795 MB memory, 22.5% GPU
Bounty 6: 14.4% CPU, 804 MB memory, 23.1% GPU
Bounty 7: 17.6% CPU, 848 MB memory, 26.8% GPU
Bounty 8: 16.2% CPU, 865 MB memory, 31.3% GPU
Bounty 9: 18.7% CPU, 909 MB memory, 17.8% GPU
Bounty 10: 20.9% CPU, 974 MB memory, 22.1% GPU
Bounty 11: 26.0% CPU, 1136 MB memory, 25.8% GPU
Bounty 12: 26.7% CPU, 1145 MB memory, 20.9% GPU
Bounty 13: 29.3% CPU, 1153 MB memory, 30.9% GPU
Bounty 14: 34.4% CPU, 1165 MB memory, 52.9% GPU
Bounty 15: 33.6% CPU, 1172 MB memory, 29.2% GPU
Bounty 16: 35.6% CPU, 1184 MB memory, 33.5% GPU
Bounty 17: 35.7% CPU, 1220 MB memory, 34.7% GPU
Bounty 18: 46.1% CPU, 1255 MB memory, 38.1% GPU
Bounty 19: 43.9% CPU, 1376 MB memory, 36.3% GPU
Bounty 20: 43.4% CPU, 1478 MB memory, 35.6% GPU

That should be enough of a proof. Not just a memory leak, but massive leak also on whatever keeps eating the CPU.