split with bean: multithreading problem

Hello,

most of our routes contain a split with bean functionallity.

For example:
.split().method(Myclass.class.getName(), "method")
or
.split(bean(MyClass.class.getName(), "method"))

Sometimes we got strange behavior in this routes and now I've found why:
Although the bean MyClass was given to the splitter as "beanRef", the
behavior is like a singleton.

I've tried a lot of variants of split().method, split(bean(....)), bean as
string, class, object(=instance) but the bean MyClass everytime had the same
instance.

Maybe I've missed something, but I think that's not the way it should
behave.

Am I wrong with this?

kind regards,
Christoph