TimingKey Memory Leak

[zizhong]

Currently, TimingKey is implemented with a concurrent hashmap. TimingKey currently only provides registerKey to add an entry to the hashmap.
Each HTTPClient will create several different filters. Each filter will trigger registerKey several times.
There is no mechanism to reclaim the memory after the filters are unreachable.

If an app keeps creates new HTTPClients, the issue becomes more obvious.