Actually, it's already fixed by the rewrite of EmbeddableComponentManager in 3.4 but still present in the 3.3 branch.