java client auto updating value cause memory leak

[libinglong]

• I have searched the issues of this repository and believe that this is not a duplicate.
• I have checked the FAQ of this repository and believe that this is not a duplicate.

Describe the bug
A clear and concise description of what the bug is.

the class ApolloProcessor is used to auto update the config value.
so we must store the bean so that we can update.
BUT,when we use prototype bean to do something,it becomes dangerous.
After creating the bean with beanfactory or applicationContext and doing something,
the bean should be recyclable.BUT now it is store in somewhere(the queue in thread pool or springValueRegistry) with strong refrence.

To Reproduce
Steps to reproduce the behavior:
1. using prototype bean to do something repeatedly

Expected behavior
A clear and concise description of what you expected to happen.

memory leak

[nobodyiam]

I think this was fixed by #1676

[libinglong]

I think this was fixed by #1676

thank you!
I should update my client version
by the way.
the spring bean can be recyclable now,but SpringVaule object in registry not.
should we ignore it as it just use very little space and cpu

[nobodyiam]

I think the same pr also added the clean up mechanism for SpringValue objects

https://github.com/ctripcorp/apollo/blob/4d56835c4979b372bf635eb42db98694d9e9fd7a/apollo-client/src/main/java/com/ctrip/framework/apollo/spring/property/SpringValueRegistry.java#L63

[libinglong]

I think the same pr also added the clean up mechanism for SpringValue objects

https://github.com/ctripcorp/apollo/blob/4d56835c4979b372bf635eb42db98694d9e9fd7a/apollo-client/src/main/java/com/ctrip/framework/apollo/spring/property/SpringValueRegistry.java#L63

oh,sorry for my disregard.
I thought it was going to use CopyOnWriteArrayList to make thread safe on regist and removing.