Does AML need to support more than 95 aliases per location?

Accounts that include locations with more than 95 aliases will fail deployment. Currently aliases do not exist for the US taxonomy. The Japanese taxonomy has 8 that exceed 95 aliases:

This is the list of 8 location ID’s that hit the existing limit of 96 for JP Taxonomy.

+------------+------------+
| locationID | aliasCount |
+------------+------------+
|     220106 |        668 |
|     220084 |        179 |
|     220101 |        136 |
|     220102 |        120 |
|     220071 |        112 |
|     220054 |        105 |
|     220087 |         98 |
|     220088 |         97 |
+------------+------------+

One consideration is that an adgroup is created (in the GM camapign) for each alias. Additionally, all geo-modified keyword is duplicated for each alias. This can lead to 10's of thousands of geo-modified keywords. The affect of this is that deployments are much slower, more quota is used, and keyword updates take a lot longer. On a lesser concern, more disk space is used.