To elaborate on Tilman's comment,
Just because you can do something doesn't mean you should. There are computers that don't have much fonts and the result may be weird
They're entirely correct: don't do this, use subset embedding because different setups can have different versions of Arial all of which will resolve against the ArialMT identifier, but with completely different internal glyphIDs.
As PDFs point to glyphids, not 'letters', what looks like cake
with your copy of Arial could —when encoded as glyphid array— end up being B^r(
in a different version of Arial. And that even includes newer versions of Arial that you yourself might end up using a year from now: suddenly your PDF files are completely unusable even for you.
PDF should be stand-alone documents. If you want people to read your PDFs, use subset embedding for the fonts you used, even if they're supposedly "generally available". The only way to not embed a font is to make the document use only fonts from the predefined standard set of 14 fonts, which any PDF-spec compliant reader must come with in order to render content without font embeds. And notice that Arial is not in that list.