Little suggestion to the dev team: when dropping the block size limit, also consider implementing "replacement code" that would give block generators the ability to control the block limit themselves through soft-limits.
Block size soft limit is already a configurable parameter inside bitcoind.
I'm not sure we're talking the same thing here.
What I call "soft limit" is not a personal limit on the blocks you'll generate or relay.
What I mean would be a set of value-pairs (X,Y), where X is a limit for block acceptance, and Y is the number of block deeps a third-party block violating X needs to be in the chain for you to accept to mine on top of it.
For example, let's say, for block size soft limit you set (1Mb, 1), (5Mb, 2) and (10Mb, 3). That means that if you receive a block larger than 1Mb, you refuse to build on top of it, unless it has already another block on top of it. For >5Mb, it needs to be 2 blocks deep. For 10Mb, 3 blocks deep and so on.
I also strongly suggest soft-limits on "percentage of unknown transactions (not in memory pool)", because that's how a spammer-miner would create gigantic blocks: by filling it with transactions that he does not intend to broadcast, as that would require paying lots of fees.
AFAIK none of these are implemented, right?