Thanks for reply.
No, there is only one app and only one bean with such name. Renaming bean helps, but this issue can happen with new name another time, so, I need to rename it again and again. Looks like it is related to EJBTHREE-2209, because it happens only when previous deploy was unsuccessfull.