It does. SEG V2 + Boxer is what we run and we had this issue.

Follow the steps for 'Scenario 3: Native client with SEG Proxy' - ActiveSync as a protocol doesn't care if you're using Boxer or native as your client. Be sure to check it on the Exchange server end as well: Configure client-specific message size limits | Microsoft Docs