I don't think it would be removed because the pre-compiled views are still using can.EJS and can.Mustache (see the can-compile tests). EJS and Mustache depend on the scanner code (even though it isn't used with pre-compiled views).
At the moment there isn't a production specific EJS or Mustache module. The question is if it would be worth getting rid of the template scanning functionality just to save about 1.5k (it's shared between EJS and Mustache). Especially since you might still need it for inline templates or loading a template dynamically.