Alternatively to those two, you might create (and dispose) your own EmbeddedCacheManager, but keep in mind that all the beans will still be there in BeanManager. So later on during the development you might get some weird errors.

Thanks for the heads up! There was another commit (which didn't get into Alpha3 but will be in Alpha4) that fixed this problem [1]. You may give it a go and use our SNAPSHOTs (here is an updated reproducer with [2])